Package | hl7.fhir.us.davinci-pdex |
Type | OperationDefinition |
Id | Id |
FHIR Version | R4 |
Source | http://hl7.org/fhir/us/davinci-pdex/https://build.fhir.org/ig/HL7/davinci-epdx/OperationDefinition-bulk-member-match.html |
Url | http://hl7.org/fhir/us/davinci-pdex/OperationDefinition/bulk-member-match |
Version | 2.1.0 |
Status | active |
Date | 2024-12-13T18:03:36+00:00 |
Name | BulkMemberMatch |
Title | PDex Bulk Member Match Operation |
Experimental | False |
Realm | us |
Authority | hl7 |
Description | The **$bulk-member-match** operation that can be invoked by either a payer or an EHR or other system, allows one health plan to retrieve a unique identifier for a group resource containing matched members from another health plan using a member's demographic, coverage information with an accompanying consent record. This identifier can then be used to perform subsequent queries and operations. Health Plans implementing a deterministic match will require a match on member id or subscriber id at a minimum (i.e. A pure demographic match will not be supported by such implementations.). |
Type | true |
Kind | operation |
CapabilityStatement | |
pdex-payer-access-server | PDex Payer Access Server CapabilityStatement |
pdex-server-6-1 | PDex Server CapabilityStatement with US core 6.1 support |
pdex-server | PDEX Server CapabilityStatement |
No resources found
Note: links and images are rebased to the (stated) source
Generated Narrative: OperationDefinition bulk-member-match
URL: [base]/Group/$bulk-member-match
Input parameters Profile:PDex $multi-member-match request
Output parameters Profile:PDex $multi-member-match response
Use | Name | Scope | Cardinality | Type | Binding | Documentation |
IN | MatchRequest | 1..1 | Reference (PDex $multi-member-match request) | Bundle of Member information. Repeat bundle for each member to be submitted to bulk member-match, as defined in PDex $multi-member-match request. | ||
OUT | MatchResponse | 1..1 | Reference (PDex $multi-member-match response) | Bundle of Groups returned from Member Match Operation. There can be up to three (3) groups: Matched, Not-Matched and ConsentConstrained. |
{
"resourceType" : "OperationDefinition",
"id" : "bulk-member-match",
"text" : {
"status" : "generated",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\"><p class=\"res-header-id\"><b>Generated Narrative: OperationDefinition bulk-member-match</b></p><a name=\"bulk-member-match\"> </a><a name=\"hcbulk-member-match\"> </a><a name=\"bulk-member-match-en-US\"> </a><p>URL: [base]/Group/$bulk-member-match</p><p>Input parameters Profile:<a href=\"StructureDefinition-pdex-parameters-multi-member-match-bundle-in.html\">PDex $multi-member-match request</a></p><p>Output parameters Profile:<a href=\"StructureDefinition-pdex-parameters-multi-member-match-bundle-out.html\">PDex $multi-member-match response</a></p><h3>Parameters</h3><table class=\"grid\"><tr><td><b>Use</b></td><td><b>Name</b></td><td><b>Scope</b></td><td><b>Cardinality</b></td><td><b>Type</b></td><td><b>Binding</b></td><td><b>Documentation</b></td></tr><tr><td>IN</td><td>MatchRequest</td><td/><td>1..1</td><td><a href=\"http://hl7.org/fhir/R4/references.html#Reference\">Reference</a> (<a href=\"StructureDefinition-pdex-parameters-multi-member-match-bundle-in.html\" title=\"http://hl7.org/fhir/us/davinci-pdex/StructureDefinition/pdex-parameters-multi-member-match-bundle-in\">PDex $multi-member-match request</a>)</td><td/><td><div><p>Bundle of Member information. Repeat bundle for each member to be submitted to bulk member-match, as defined in PDex $multi-member-match request.</p>\n</div></td></tr><tr><td>OUT</td><td>MatchResponse</td><td/><td>1..1</td><td><a href=\"http://hl7.org/fhir/R4/references.html#Reference\">Reference</a> (<a href=\"StructureDefinition-pdex-parameters-multi-member-match-bundle-out.html\" title=\"http://hl7.org/fhir/us/davinci-pdex/StructureDefinition/pdex-parameters-multi-member-match-bundle-out\">PDex $multi-member-match response</a>)</td><td/><td><div><p>Bundle of Groups returned from Member Match Operation. There can be up to three (3) groups: Matched, Not-Matched and ConsentConstrained.</p>\n</div></td></tr></table></div>"
},
"extension" : [
{
"url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
"valueCode" : "fm"
},
{
"url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status",
"valueCode" : "trial-use",
"_valueCode" : {
"extension" : [
{
"url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
"valueCanonical" : "http://hl7.org/fhir/us/davinci-pdex/ImplementationGuide/hl7.fhir.us.davinci-pdex"
}
]
}
}
],
"url" : "http://hl7.org/fhir/us/davinci-pdex/OperationDefinition/bulk-member-match",
"version" : "2.1.0",
"name" : "BulkMemberMatch",
"title" : "PDex Bulk Member Match Operation",
"status" : "active",
"kind" : "operation",
"date" : "2024-12-13T18:03:36+00:00",
"publisher" : "HL7 International / Financial Management",
"contact" : [
{
"name" : "HL7 International / Financial Management",
"telecom" : [
{
"system" : "url",
"value" : "http://www.hl7.org/Special/committees/fm"
},
{
"system" : "email",
"value" : "fm@lists.HL7.org"
}
]
},
{
"name" : "Mark Scrimshire (mark.scrimshire@onyxhealth.io)",
"telecom" : [
{
"system" : "email",
"value" : "mailto:mark.scrimshire@onyxhealth.io"
}
]
},
{
"name" : "HL7 International - Financial Management",
"telecom" : [
{
"system" : "url",
"value" : "http://www.hl7.org/Special/committees/fm"
}
]
}
],
"description" : "The **$bulk-member-match** operation that can be invoked by either a payer or an EHR or other system, allows one health plan to retrieve a unique identifier for a group resource containing matched members from another health plan using a member's demographic, coverage information with an accompanying consent record. This identifier can then be used to perform subsequent queries and operations. Health Plans implementing a deterministic match will require a match on member id or subscriber id at a minimum (i.e. A pure demographic match will not be supported by such implementations.).",
"jurisdiction" : [
{
"coding" : [
{
"system" : "urn:iso:std:iso:3166",
"code" : "US",
"display" : "United States of America"
}
]
}
],
"affectsState" : true,
"code" : "bulk-member-match",
"resource" : [
"Group"
],
"system" : false,
"type" : true,
"instance" : false,
"inputProfile" : "http://hl7.org/fhir/us/davinci-pdex/StructureDefinition/pdex-parameters-multi-member-match-bundle-in",
"outputProfile" : "http://hl7.org/fhir/us/davinci-pdex/StructureDefinition/pdex-parameters-multi-member-match-bundle-out",
"parameter" : [
{
"name" : "MatchRequest",
"use" : "in",
"min" : 1,
"max" : "1",
"documentation" : "Bundle of Member information. Repeat bundle for each member to be submitted to bulk member-match, as defined in PDex $multi-member-match request.",
"type" : "Reference",
"targetProfile" : [
"http://hl7.org/fhir/us/davinci-pdex/StructureDefinition/pdex-parameters-multi-member-match-bundle-in"
]
},
{
"name" : "MatchResponse",
"use" : "out",
"min" : 1,
"max" : "1",
"documentation" : "Bundle of Groups returned from Member Match Operation. There can be up to three (3) groups: Matched, Not-Matched and ConsentConstrained.",
"type" : "Reference",
"targetProfile" : [
"http://hl7.org/fhir/us/davinci-pdex/StructureDefinition/pdex-parameters-multi-member-match-bundle-out"
]
}
]
}
XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.